Usage license

ABSTRACT

A system is configured to receive a task. The task is received over a first network, includes authentication credentials, and is processed using an application. The system is further configured to send the authentication credentials to a licensing server. The authentication credentials are sent over a second network, and are sent prior to processing the task using the application. The system is also configured to receive an authorization. The authorization is received over the second network, and authorizes the application to process the task.

REFERENCE TO RELATED APPLICATIONS

This application also claims priority to U.S. Provisional PatentApplication No. 61/494,270, filed on Jun. 7, 2011, and to U.S.Provisional Patent Application No. 61/494,259, filed on Jun. 7, 2011.The contents of all the aforementioned applications are incorporated byreference.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate one or more implementationsdescribed herein and, together with the description, explain theseimplementations. In the drawings:

FIG. 1 is a diagram of an example environment in which systems and/ormethods described herein may be implemented;

FIG. 2 is a diagram of example components of one or more devices of FIG.1;

FIG. 3 is a diagram of example functional components of a worker of FIG.1;

FIG. 4 is a diagram of example functional components of a licensingserver of FIG. 1;

FIG. 5 is a flowchart of an example process for processing a task basedon a license;

FIG. 6 is a flowchart of an example process for providing authorizationbased on a license;

FIGS. 7A-7F illustrate an example of processing a task; and

FIGS. 8A-8D illustrate another example of processing a task.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

Embodiments described herein may allow a worker to receive a request touse an instance of software to process a task based on a licenseassociated with a licensee. The license may provide a pay-per-usagemodel that allows the licensee to pay for the use of the additionalinstance of software based on an amount (e.g., a period of time) of theuse. The worker may request and receive, from a licensing server,authorization to process the task based on the license. Once authorizedto process the task, the worker may continuously transmit, to thelicensing server, heartbeats that indicate that the worker is continuingto process the task based on the license. The licensing server maydetermine whether the worker is allowed to continue to process the taskbased on a usage amount associated with the license. The licensingserver may terminate processing of the task, by the worker, when theusage amount exceeds an account value (e.g., a usage account value)associated with the license.

Example Environment

FIG. 1 is a diagram of an example environment 100 in which systemsand/or methods described herein may be implemented. Environment 100 mayinclude one or more of the following components: a client device 110, afirst network 120, a first worker 130, a licensing server 140, and asecond network 150. In practice, environment 100 may include additionalcomponents, fewer components, different components, or differentlyarranged components than are shown in FIG. 1. Additionally, oralternatively, one or more of the components of environment 100 mayperform one or more functions described as being performed by anotherone or more of the components of environment 100.

Furthermore, two or more of the components, of FIG. 1, may beimplemented within a single device, or a single component may beimplemented as multiple, distributed devices. Also, components ofenvironment 100 may interconnect via wired and/or wireless connections.In other words, any two components, of environment 100, may communicatevia a wired connection, a wireless connection, or a combination of awired connection and a wireless connection.

Client device 110 may include a computation and/or communication device,such as a device that is capable of invoking one or more workers forperforming a job. In one implementation, client device 110 may take theform of a computer, including a web service terminal, a personalcomputer, a laptop, a tablet computer, a smart phone, a mobile telephonedevice, a personal digital assistant (PDA), etc.

Client device 110 may execute an application 160. A user of clientdevice 110 may use application 160 to create a task. The task mayinclude, for example, executing a model (e.g., created by the userutilizing application 160), determining a solution to a problem, and/oranother collection of computation tasks. In some instances, clientdevice 110 may determine that client device 110 requires an additionalinstance of application 160 to process the task (e.g., to generate aresult within a certain period of time). In other instances, the usermay request that client device 110 use an additional instance ofapplication 160 to process the task.

In one implementation, client device 110 may request authorization fromlicensing server 140 to use the other instance of application 160 toprocess the task. In another implementation, client device 110 maytransmit the task to first worker 130 via first network 120, and firstworker 130 may request, from licensing server 140, authorization to usean instance of application 160.

Each one of first network 120 and second network 150 may include asingle network or multiple networks of a same type or different types.For example, first network 120 and/or second network 150 may include adirect connection between devices, a local area network (LAN), a widearea network (WAN) (e.g., the Internet), a metropolitan area network(MAN), a wireless network (e.g., a general packet radio service (GPRS)network), a telephone network (e.g., a Public Switched Telephone Networkand/or a cellular network), a subset of the Internet, an ad hoc network,or any combination of the aforementioned networks.

In one implementation, first network 120 and/or second network 150 mayinclude a cloud and/or a private network that provides computationalresources on demand. In another implementation, first network 120 and/orsecond network 150 may include a public network, an insecure network,etc.

First worker 130 may be part of a group of workers that make up adistributed computing system (DCS) and/or a parallel computing system.First worker 130 may include an autonomous computer device thatcommunicates with other workers via first network 120. First worker 130may process a task (e.g., solve a computational problem) that has beenprovided by client device 110.

Licensing server 140 may include a computation and/or communicationdevice, such as a device that is capable of communicating with firstworker 130, network 150, etc. Licensing server 140 may represent asingle server device or multiple server devices and/or computer systems.As described further below in reference to FIG. 4, licensing server 140may store license information associated with a license. Licensingserver 140 may provide authentication credentials to client device 110to grant client device 110 an additional instance of application 160based on a license associated with the authentication credentials.Licensing server 140 may also provide authorizations, in response toauthorization requests that include the authentication credentials, toclient device 110 and/or first worker 130 to use an additionalapplication 160 to process tasks created by client device 110.

Example Components of a Device

FIG. 2 is a diagram of example components of a device 200 that maycorrespond to client device 110, first worker 130, and/or licensingserver 140. Each one of client device 110, nodes 130, and/or licensingserver 140 may include one or more devices 200.

As shown in FIG. 2, device 200 may include a bus 210, a processor 220, amemory 230, an input component 240, an output component 250, and acommunication interface 260. In another implementation, device 200 mayinclude additional components, fewer components, different components,and/or differently arranged components than are shown in FIG. 2.Additionally, or alternatively, one or more components of device 200 mayperform one or more tasks described as being performed by one or moreother components of device 200.

Bus 210 may include a path that permits communication among thecomponents of device 200. Processor 220 may include a processor,microprocessor, or processing logic that may interpret and executeinstructions. Memory 230 may include a dynamic storage device that maystore information and instructions for execution by processor 220,and/or a type of non-volatile storage device that may store informationfor use by processor 220.

Input component 240 may include one or more input mechanisms that permita user to input information to device 200. Output component 250 mayinclude one or more output mechanisms that output information to theuser. Examples of input and output mechanisms may include buttons; atouch screen interface to permit data and control commands to be inputinto device 200; a speaker to receive electrical signals and outputaudio signals; a microphone to receive audio signals and outputelectrical signals; a display to output visual information; etc.

Communication interface 260 may include any transceiver-like mechanismthat enables device 200 to communicate with other devices and/orsystems. For example, communication interface 260 may include anEthernet interface, an optical interface, a coaxial interface, awireless interface, or the like.

Device 200 may perform certain operations described herein. Device 200may perform these operations in response to processor 220 executingsoftware instructions (e.g., computer program(s)) contained in acomputer-readable medium, such as memory 230, a secondary storage device(e.g., hard disk, CD-ROM, etc.), or other forms of random-access memory(RAM) or read-only memory (ROM). A computer-readable medium may bedefined as a non-transitory memory device. A memory device may includespace within a single physical memory device or spread across multiplephysical memory devices. The software instructions may be read intomemory 230 from another computer-readable medium or from another device.The software instructions contained in memory 230 may cause processor220 to perform processes described herein. Alternatively, hardwiredcircuitry may be used in place of or in combination with softwareinstructions to implement processes described herein. Thus,implementations described herein are not limited to any specificcombination of hardware circuitry and software.

Example Functional Components of Worker

FIG. 3 is a diagram of example functional components of first worker130. As shown in FIG. 3, first worker 130 may include an authenticationcredentials component 310, a heartbeat component 320, and/or a taskprocessing component 330. In practice, first worker 130 may includeadditional functional components, fewer functional components, and/ordifferent functional components than are shown in FIG. 3.

Authentication credentials component 310, heartbeat component 320,and/or task processing component 330 may be implemented using one ormore of the components of device 200 of FIG. 2. For example,authentication credentials component 310, heartbeat component 320,and/or task processing component 330 may be implemented via processor220 executing instructions stored in memory 230.

Authentication credentials component 310 may receive authenticationcredentials from client device 110. In one implementation,authentication credentials component 310 may receive the authenticationcredentials with a task provided by client device 110. Alternatively,authentication credentials component 310 may receive the authenticationcredentials at another time. For example, authentication credentialscomponent 310 may, in response to receiving a task from client device110, request the authentication credentials from client device 110.

In any event, authentication credentials component 310 may generate anauthorization request that includes the authentication credentials.Authentication credentials component 310 may transmit the authorizationrequest to licensing server 140. Authentication credentials component310 may receive, from licensing server 140 and when the authenticationcredentials have been properly authorized, an authorization in responseto the authorization request. When authentication credentials component310 receives the authorization, authentication credentials component 310may instruct heartbeat component 320 to begin transmitting heartbeats tolicensing server 140, and may instruct task processing component 330 tobegin processing the task.

Heartbeat component 320 may transmit heartbeats to licensing server 140while task processing component 330 is processing the task. For example,heartbeat component 320 may generate a heartbeat, and may transmit theheartbeat to licensing server 140. Heartbeat component 320 may receive,from licensing server 140, a heartbeat response in response to theheartbeat. Heartbeat component 320 may periodically (e.g., every 1minute) send a new heartbeat to licensing server 140. A heartbeat maydirectly or indirectly indicate a status or a state of first worker 130.In one implementation, a heartbeat may indicate that task processingcomponent 330 is processing the task. In another implementation, aheartbeat may include a ping that does not include any content. In yetanother implementation, a heartbeat may include a message that includescontent. Licensing server 130 may process the content to determineinformation about first worker 130. For example, a heartbeat may includeusage information that may be used to calculate an amount of theprocessing (e.g., a period of time spent by task processing component330 to process the task).

Heartbeat component 320 may determine whether task processing component330 is authorized to continue to process the task. When heartbeatcomponent 320 determines that task processing component 330 is notauthorized to continue to process the task, heartbeat component 320 mayinstruct task processing component 330 to terminate processing of thetask. When heartbeat component 320 determines that task processingcomponent 330 is authorized to continue to process the task, heartbeatcomponent 320 may generate a new heartbeat, and may transmit the newheartbeat to licensing server 140.

Task processing component 330 may process the task. For example, taskprocessing component 330 may initialize an application to process thetask after receiving the instructions to begin processing the task fromauthentication credentials component 310. Task processing component 330may use the application to process the task until the task is processedor until receiving the instruction to terminate the processing of thetask from heartbeat component 320. Task processing component 330 mayfurther generate a result based on the processing of the task, and maytransmit the result to client device 110.

Example Functional Components of Licensing Server

FIG. 4 is a diagram of example functional components of licensing server140. As shown in FIG. 4, licensing server 140 may include a licenseeinformation component 410, an authentication component 420, and/or ausage tracker component 430. In practice, licensing server 140 mayinclude additional functional components, fewer functional components,and/or different functional components than are shown in FIG. 4.Licensee information component 410, authentication component 420, and/orusage tracker component 430 may be implemented using one or more of thecomponents of device 200 of FIG. 2. For example, licensee informationcomponent 410, authentication component 420, and/or usage trackercomponent 430 may be implemented via processor 220 executinginstructions stored in memory 230.

Licensee information component 410 may store information about licensesthat are associated with licensees (e.g., client device 110 or a user ofclient device 110) and that permit the licensees to use instances ofapplications. For example, an operator of licensing server 140 may enterinformation about licensees into licensee information component 410. Theinformation may include, for example, an identifier associated with alicensee, authentication credentials (e.g., a username, a password, adigital certificate, etc.) used to authenticate the licensee,authentication information (e.g., a token) that a worker has to provideto receive authorization to process a task for the licensee, informationidentifying an application that may be used to process a task based onelicense of the licensee, terms of the license, an account valueassociated with the license, a total usage amount that represents anamount of processing performed by the worker based on the license, etc.Licensee information component 410 may include one or more datastructures, database records, files, etc., residing in acomputer-readable storage medium. Licensee information component 410 maybe configured to provide licenses to licensees over a network, such asfirst network 120 or second network 150.

Authentication component 420 may provide authorization to allow aworker, such as first worker 130, to initialize an application toprocess a task. For example, authentication component 420 may receive anauthorization request from first worker 130 to process a task receivedfrom client device 110. The authorization request may includeauthentication credentials.

Authentication component 420 may determine, based on the authenticationcredentials, whether first worker 130 is authorized to use a particularapplication to process the task based on a license associated withclient device 110 or a user of client device 110. If properlyauthenticated, authentication component 420 may transmit anauthorization to first worker 130 to authorize first worker 130 toprocess the task.

In one implementation, when authentication component 420 determines thatfirst worker 130 is authorized to use a particular application toprocess the task, licensing server 140 may check-out a license to firstworker 130 to be used to process the task. First worker 130 may spawn anew process, based on the license, to use the particular application toprocess the task. When first worker 130 determines that the particularapplication exits, first worker 130 may check-in the license back tolicensing server 140. The particular application may exit, for example,when the particular application finishes completing the task or when theparticular application crashes. Additionally, or alternatively,licensing server 140 may check-in the license when licensing service 140determines that first worker 130 and/or the particular applicationcrashes.

Usage tracker component 430 may track an amount of processing performedby a worker based on a license. For example, usage tracker component 430may receive a heartbeat from first worker 130. Usage tracker component430 may determine usage information based on the heartbeat. The usageinformation may include, for example, an amount of time and/or anothertype of information used to measure processing performed by first worker130. Usage tracker component 430 may determine a total usage amountbased on the usage information. Usage tracker component 430 may updatethe total usage amount based on subsequently received heartbeats. Usagetracker component 430 may determine, based on the updated total usageamount, whether first worker 130 is allowed to continue processing thetask associated with the usage license. Usage tracker component 430 maytransmit, to first worker 130, a heartbeat response in response to theheartbeat. The heartbeat response may indicate whether first worker 130is allowed to continue to use the particular application to process thetask based on the license. For example, a heartbeat response may includeinstructions to terminate the processing of the task, by first worker130, when usage tracker component 430 determines that the total usageamount has reached a particular threshold associated with the license.

In one implementation, licensing server 140 may generate a heartbeatresponse that includes a remote kill. In one example, licensing server140 may include the remote kill in the heartbeat response when theupdated total usage amount is greater than the particular threshold.

In another example, licensing server 140 may include the remote kill inthe heartbeat response based on change(s) in other value(s) associatedwith the usage license. For example, licensing server 140 may includethe remote kill in the heartbeat response when a value associated withthe usage license indicates that the licensee associated with the usagelicense has not paid a bill per the usage license. In yet anotherexample, licensing server 140 may include remote kill in the heartbeatresponse based on instructions from an administrator of the usagelicense (e.g., an operator of licensing server 140). The instructionsmay, for example, instruct licensing server 140 to terminate processingby workers, including first worker 130, based on the usage license orfor the licensee.

In another implementation, licensing server 140 may generate a heartbeatresponse that includes instructions for sending heartbeats to licensingserver 140. In one example, the instructions may include an interval atwhich future heartbeats should be sent from first worker 130 tolicensing server 140. In another example, the instructions may specify adowntime during which heartbeats should not be sent from first worker130 to licensing server 140. For example, licensing server 140 mayreceive information from, for example, an operator of licensing server140 that indicates that licensing server 140 will not be able to receiveheartbeats and/or transmit heartbeat responses (e.g., because licensingserver 140 will be shut down and/or undergoing maintenance) during aparticular period of time. In response to the information, licensingserver 140 may generate a heartbeat response that includes instructionsfor first worker 130 not to send heartbeats to licensing server 140during the particular period of time.

Example Processes

FIG. 5 is a flowchart of an example process 500 for processing a taskbased on a license. In one implementation, first worker 130 may performprocess 500. In another implementation, a device or collection ofdevices separate from, or in combination with, first worker 130 mayperform some or all of process 500. For example, client device 110 mayact as first worker 130, and may perform some or all of process 500. Inaddition, other implementations of process may include fewer blocks,additional blocks, blocks in orders differing from those of FIG. 5 ifdesired. In addition, blocks in FIG. 5 can be combined without departingfrom the spirit and scope of the invention.

As shown in FIG. 5, process 500 may include receiving a task (block505). In one implementation, prior to process 500, client device 110 mayinitiate a process to use additional processing power to process a task.First worker 130 may receive the task from client device 110 via firstnetwork 120. First worker 130 may receive the task based on clientdevice 110 interacting with a web service. In another implementation,first worker 130 may receive the task from another worker. In yetanother implementation, first worker 130 may receive the task from ascheduler operating on behalf of client device 110 or the other worker.

In one example, the task may include authentication credentials and/oridentify a particular license to be used to process the task. Asindicated above, the authentication credentials associated with clientdevice 110 or a user of client device 110. In another example,authentication credentials component 310 (FIG. 3), of first worker 130,may programmatically generate the authentication credentials based oninformation included in the task. The authentication credentials mayinclude a user name, a password, a token, a digital certificate, abiometric identifier, and/or other types of information. Theauthentication credentials may be received by using a standard protocol.The standard protocol may include, for example, a hypertext transferprotocol (http) or a hypertext transfer protocol secure (https).

Process 500 may further include transmitting an authorization requestmessage to a licensing server (block 510), receiving and processingauthorization information (block 515), and determining whetherauthorization is received (block 520). For example, authenticationcredentials component 310 may generate an authorization request message.The authorization request message may include the authenticationcredentials. Authentication credentials component 310 may transmit theauthorization request message to licensing server 140 via second network150. Authentication credentials component 310 may transmit theauthorization request message by using, for example, a securecommunications protocol, a web service, or a remote method invocation(RMI).

In one implementation, the authorization request message may be sent onbehalf of the application to be used to process the task. Authenticationcredentials component 310 may receive, from licensing server 140 and viasecond network 150, authorization information in response to theauthorization request message. Authentication credentials component 310may process the authorization information to determine whether firstworker 130 is authorized to use the application to process the task.

If the authentication information indicates that the worker is notauthorized to use the application (block 520—NO), process 500 mayinclude transmitting an authorization failure message (block 525). Forexample, authentication credentials component 310 may determine that theauthentication information indicates that first worker 130 is notauthorized to use the application when the authorization informationindicates that the first worker 130 is not authorized to use theapplication to process the task. When the authorization is not received,authentication credentials component 310 may transmit an authorizationfailure message to client device 110. The authorization failure messagemay indicate that licensing server 140 did not authorize first worker130 to process the task based on the license associated with theauthentication credentials.

In another implementation, authentication credentials component 310 maydetermine at the first worker 130 is not authorized to use theapplication to process the task because first worker 130 is notauthorized to process tasks of a particular type of the task. Forexample, first worker 130 may only process academic tasks. The task maybe a corporate task. Authentication credentials component 310 maydetermine that first worker 130 is not authorized to process the taskbecause the task is not an academic type of task. In this example, firstworker 130 may forward the task to another worker that processescorporate tasks. In yet another implementation, licensing server 140 mayforward the task from first worker 130 to the other worker thatprocesses corporate tasks.

If the authentication information indicates that the worker isauthorized to use the application (block 520—YES), process 500 mayinclude initializing the application (block 530). For example,authentication credentials component 310 may determine that theauthentication information indicates that first worker 130 is authorizedto use the application when the authorization information indicates thatfirst worker 130 is authorized to use the application to process thetask. When the authorization is received, task processing component 330(FIG. 3), of first worker 130, may initialize the application, forprocessing the task, in accordance with the license associated with theauthentication credentials.

Alternatively, first worker 130 may initialize the application before orduring the transmission of the authorization request message. Forexample, first worker 130 may use the application to transmit theauthorization request message (block 510) and/or to receive and processthe authorization information (block 515). First worker 130 may use theapplication to process the task only after the authorization isreceived.

Process 500 may also include processing the task (block 535), producinga result (block 540), and transmitting the result (block 545). Forexample, after first worker 130 receives the indication from licensingserver 140 that first worker 130 is authorized to use the application toprocess the task, task processing component 330 may use the applicationto process the task.

Additionally, or alternatively, processing the task may includetransmitting a sub-task, of the task, to a different worker for thedifferent worker to use a different application to process the sub-taskon behalf of the application of first worker 130. The request mayinclude the authentication credentials. The different worker may processthe sub-task after receiving authorization to process the sub-task fromlicensing server 140. First worker 130 may receive, from the differentworker, the result from processing the sub-task.

In either event, task processing component 330 may produce a result. Theresult may be based on processing performed by first worker 130 and,when used, one or more different workers. First worker 130 may transmitthe produced result to client device 110.

While initializing and/or processing the task (block 535), process 500may include producing a heartbeat (block 550), transmitting theheartbeat to the licensing server (block 555), receiving a heartbeatresponse (block 560), and determining whether to continue processing thetask (block 565). For example, after the authorization is receivedand/or while processing the task, heartbeat component 320 (FIG. 3), offirst worker 130, may produce a heartbeat. The heartbeat may indicatethat the application is being used to process the task. Heartbeatcomponent 320 may transmit, via second network 150, the heartbeat tolicensing server 140. Heartbeat component 320 may receive, via secondnetwork 150 and from licensing server 140, a heartbeat response inresponse to the heartbeat. The heartbeat response may indicate whetherfirst worker 130 remains authorized to continue using the application toprocess the task. Heartbeat component 320 may determine whether tocontinue processing the task based on the heartbeat response.

If the worker remains authorized to continue processing the task (block555—YES), process 500 may include producing a new heartbeat (block 550).For example, when heartbeat component 320 determines that first worker130 remains authorized to continue processing the task, task processingcomponent 330 may continue to process the task, and heartbeat component320 may produce a new heartbeat. Heartbeat component 320 maycontinuously produce heartbeats until task processing component 330finishes processing the task or until first worker 130 determines thatfirst worker 130 does not remain authorized to continue processing thetask.

If the worker does not remain authorized to continue processing the task(block 565—NO), process 500 may include terminating processing (block570), transmitting a notification and/or a partial result (block 575),and terminating the application and/or shutting down a worker (block580). For example, when heartbeat component 320 determines that firstworker 130 does not remain authorized to continue to process the task,first worker 130 may terminate the processing of the task. Thereafter,first worker 130 may transmit a notification and/or a partial result toclient device 110. The notification may indicate that the processing ofthe task was not completed because first worker 130 did not receiveauthorization to continue to use the application to process the taskbased on the license associated with the authentication credentials. Thepartial result may include an output from processing a portion of thetask. Afterwards, first worker 130 may terminate the application and/orshutdown first worker 130.

Alternatively, process 500 may include terminating the applicationand/or shutting down first worker 130 (block 580) when the result ofprocessing the task is transmitted (block 545). For example, firstworker 130 may terminate the application and/or shutdown aftertransmitting the result to client device 110.

FIG. 6 is a flowchart of an example process for providing authorizationbased on a license. In one implementation, licensing server 140 mayperform process 600. In another implementation, a device or collectionof devices separate from, or in combination with, licensing server 140may perform some or all of process 600.

As show in FIG. 6, process 600 may include receiving an authorizationrequest message with authentication credentials (block 610). Forexample, first worker 130 may receive, via first network 120, a taskfrom client device 110 or another worker (not shown in FIG. 1). Inresponse to receiving the task, first worker 130 may generate anauthorization request message, as described above in connection withFIG. 5, and may transmit the authorization request message to licenseserver 140. The authorization request message may include authenticationcredentials. Authentication component 420 (FIG. 4), of licensing server140, may receive the authorization request.

Process 600 may also include transmitting authorization information(block 620). For example, authentication component 420 may use theauthentication credentials to retrieve licensee information associatedwith the license from licensee information component 410 (FIG. 4) oflicense server 140. The licensee information may identify theapplication that first worker 130 is allowed to use to process a taskreceived from client device 110. Authentication component 420 maydetermine, based on the licensee information and the authorizationrequest message, whether first worker 130 is authorized to use theapplication to process the task. In one implementation, to determinewhether first worker 130 is authorized to process the task,authentication component 420 may determine whether the authenticationcredentials are valid. Authentication component 420 may determine thatthe authentication credentials are valid when the authenticationcredentials match authentication information stored in association withthe license.

In another implementation, the licensee information may include anaccount value associated with the license. Licensing server 140 maydetermine an estimate for completing the task. Licensing server 140 maydetermine, based on the estimate, whether the account value issufficient for first worker 130 to process the task. Licensing server140 may determine that first worker 130 is allowed to process the taskwhen the account value is sufficient. For example, the account value mayequal a particular amount of money left in an account associated withthe license. In one example, the account value may equal $100.00.Licensing server 140 may estimate that $200.00 is required to processthe task. Accordingly, in this instance, licensing server 140 maydetermine that the account value is insufficient. In another example,the account value may equal $200.00. Licensing server 140 may estimatethat $100.00 is required to process the task. Accordingly, in thisinstance, licensing server 140 may determine that the account value issufficient.

Authentication component 420 may transmit, via second network 150,authorization to first worker 130 when authentication component 420determines that first worker 130 is allowed to process the task. In oneexample, authentication component 420 may generate authorizationinformation that includes the authorization, and may transmit theauthorization information to first worker 130.

Process 600 may also include receiving a heartbeat (block 630). Forexample, after receiving the authorization, first worker 130 mayinitialize the application, and may begin using the application toprocess the task. While processing the task, first worker 130 maytransmit, via second network 150, a heartbeat to licensing server 140.Licensing server 140 may receive the heartbeat. In one example,licensing server 140 may receive a first heartbeat after a first timeperiod. After block 665, as described further below, licensing server140 may receive a second heartbeat after a second time period. The firsttime period may equal the second time period.

Process 600 may also include updating a total usage amount (block 640)and determining whether an account value is sufficient (block 650). Forexample, usage tracker component 430 (FIG. 4), of licensing server 140,may update a total usage amount associated with the license, based onthe heartbeat(s) received from first worker 130. In one implementation,usage tracker component 430 may determine, based on the heartbeat(s), aperiod of time that the application has been used to process the task.Licensing server 140 may calculate a charge for the use of theapplication based on the period of time and/or one or more cost factors.The cost factors may include, for example, one or more of: a time of dayof the use of the instance of the application, a geographic location ofclient device 110, a geographic location of first worker 110, terms ofthe license, ownership information associated with client device 110, oran identity of an owner of a private network that includes first worker130. Usage tracker component 430 may increase the total usage amount byan amount of the charge. Usage tracker component 430 may determinewhether the account value, associated with the license, is sufficientbased on the updated total usage amount.

In other implementations, usage tracker component 430 may use one ormore other ways to update the total usage amount. For example, usagetracker component 430 may track a time period from when licensing server140 transmitted the authorization to first worker 130. Usage trackercomponent 430 may update the total usage amount based on the time periodand/or one or more other time periods tracked for other workers (e.g.,not shown in FIG. 1) that are processing tasks based on the license.Usage tracker component 430 may determine whether an account value issufficient based on whether the total usage amount is less than theaccount value (e.g., by a particular amount).

If the account value is not sufficient (block 650—NO), process 600 mayinclude transmitting a heartbeat response without authorization (block660). For example, usage tracker component 430 may determine that theaccount value is not sufficient when the updated total usage amount isequal to or greater than the account value or a threshold associatedwith the account value. The threshold may equal a difference between theaccount value and a particular buffer value. When usage trackercomponent 430 determines that the account value is not sufficient, usagetracker component 430 may generate a heartbeat response that indicatesthat first worker 130 is not authorized to continue using theapplication to process the task. Usage tracker component 430 maytransmit the heartbeat response, with the non-authorization indication,to first worker 130. In response to the heartbeat response, first worker130 may terminate the processing of the task, may terminate theapplication, and/or may shutdown first worker 130.

If the account value is sufficient (block 650—YES), process 600 mayinclude transmitting a heartbeat response with authorization (block665). For example, usage tracker component 430 may determine that theaccount value is sufficient when the updated total usage amount is lessthan the account value or the threshold associated with the accountvalue. When usage tracker component 430 determines that the accountvalue is sufficient, usage tracker component 430 may generate aheartbeat response that indicates that first worker 130 is authorized tocontinue using the application to process the task. Usage trackercomponent 430 may transmit the heartbeat response, with theauthorization indication, to first worker 130. In response to theheartbeat response, first worker 130 may continue to use the applicationto process the task.

Returning to FIG. 6, process 600 may also include generating andtransmitting billing information (block 670). For example, licensingserver 140 may continue receiving heartbeats (block 630) at periodicintervals, from first worker 130, until licensing server 140 transmits,to first worker 130, the heartbeat response with the non-authorizationindication or until first worker 130 finishes processing the task.Licensing server 140 may generate billing information based on the totalusage amount and/or other cost factors described above. The billinginformation may include a charge for the use of instances of theapplication. In one example, licensing server 140 may calculate a chargebased on a unit of time. For example, licensing server 140 may calculatea charge for the use of the application at a rate of $10 per minute. Iffirst worker 130 processes the task for 10 minutes, the charge may equal$100.

Additionally, or alternatively, licensing server 140 may furthergenerate the billing information based on application startupinformation that is received, for example, at a time when theapplication is initialized. The application startup information mayspecify how the licensee should be billed for processing of the task byfirst worker 130. The application startup information may include, forexample, the rate and/or when the billing information should begenerated and send to the client.

In one implementation, licensing server 140 may generate the billinginformation on a per task basis, on a time period basis (e.g., monthly),or at other times. Licensing server 140 may transmit the billinginformation to client device 110 (e.g., via email) or to the licensee inanother manner.

Licensing server 140 may also receive, while receiving heartbeats fromfirst worker 130, heartbeats from one or more other workers (not shownin FIG. 1) that are, for example, processing sub-tasks of the task.Licensing server 140 may update the total usage amount based on theheartbeats from the other workers. Licensing server 140 may alsodetermine whether the other workers are authorized to continue toprocess the sub-tasks based on the total usage amount and the accountvalue associated with the license or based on values associated withanother license, for a different application, associated with clientdevice 110 and/or the user.

Examples of Processing a Task

While the above description focused on the components in environment1100, other arrangements of components are possible. The examples belowprovide two additional example environments in which systems and methodsdescribed herein may be implemented. Other arrangements of componentsare possible.

FIGS. 7A-7F illustrate an example of processing a task in an environment700. As shown in FIGS. 7A-7F, environment 700 may include, for example,client device 110, first worker 130, licensing server 140, a firstnetwork 710, a second network 720, a second worker 730, and a thirdnetwork 750. In practice, environment 700 may include additionalcomponents, fewer components, different components, or differentlyarranged components than are shown in FIG. 7. Additionally, oralternatively, one or more of the components of environment 700 mayperform one or more functions described as being performed by anotherone or more of the components of environment 700.

Client device 110, first worker 130, licensing server 140, first network710, and third network 750 of FIG. 7 may correspond to first worker 130,licensing server 140, first network 120, and second network 150 of FIG.1, respectively. Second network 720 and second worker 730 may include asame type of components and/or perform same types of functions as firstnetwork 710 and first worker 130, respectively. First worker 130 andsecond worker 730 may operate simultaneously and/or independently of oneanother.

In this example, first worker 130 may be accessible via first network710 and second worker 730 may be accessible via second network 720.License server 140 may be accessible via third network 750. In thisexample, client device 110 may require for first worker 130 to use afirst application to process a task. The first application may requiresecond worker 730 to use a second application to process a portion ofthe task.

As shown in FIG. 7A, a user may use a client device 110 to create a task755. Client device 110 may transmit task 755, to first worker 130 viafirst network 710. Task 755 may include authentication credentialsassociated with the user or client device 110. First worker 130 maygenerate a first authorization request 760 based on task 755. Firstauthorization request 760 may request authorization to use a firstapplication to process task 755 based on a first license (e.g., aperpetual license). First authorization request 760 may also include theauthentication credentials. First worker 130 may transmit, via thirdnetwork 750, first authorization request 760 to licensing server 140.

Licensing server 140 may receive first authorization request 760directly from first worker 130 or via a first web service. Licensingserver 140 may determine, based on the authentication credentialsincluded in first authorization request 760, that first worker 130 isauthorized to use the first application to process task 755 based on thefirst license. Accordingly, licensing server 140 may generate andtransmit, via third network 750, a first authorization 765 (FIG. 7B) tofirst worker 130. In response to first authorization 765, first worker130 may use the first application to process task 755. While processingtask 755, first worker 130 may continuously transmit heartbeats (notshown in FIGS. 7A-7E) to licensing server 140 to ensure that firstworker 130 remains authorized to use the first application to processtask 755, as described above with reference to FIG. 5.

Assume that the first application of first worker 130 determines that asecond application is required to process a sub-task of task 755. Firstworker 130 may generate a request 765 (FIG. 7C) for the secondapplication to process the sub-task on behalf of the first applicationbased on the second license. Request 765 may include the sub-task andthe authentication credentials. First worker 130 may transmit, via thirdnetwork 750, request to process sub-task 765 to second worker 730.Second worker 730 may generate a second authorization request 770 (FIG.7D) based on request 765. Second authorization request 770 may alsoinclude the authentication credentials. Second authorization request 770may request authorization to process the sub-task by using the secondapplication and/or based one second license. The second license mayauthorize workers to use the second application to process tasks orsub-tasks associated with the licensee, and the first license mayauthorize workers to use the first application to process tasks orsub-tasks associated with the licensee. The terms of the first licenseand the second license may be different. Second worker 130 may transmit,via third network 750, second authorization request 770 to licensingserver 140.

Licensing server 140 may receive second authorization request 770 byusing the first web service or a second web service. Licensing server140 may determine, based on the authentication credentials included insecond authorization request 770, that second worker 730 is authorizedto use the second application to process the sub-task based on thesecond license. Accordingly, licensing server 140 may generate andtransmit, via third network 750, a second authorization 775 to secondworker 730 (FIG. 7E). Second worker 730 may receive second authorization775 by using the first web service or the second web service. Inresponse to second authorization 775, second worker 730 may use thesecond application to process the sub-task. While processing thesub-task, second worker 730 may continuously transmit heartbeats tolicensing server 140 to ensure that second worker 130 remains authorizedto process sub-task 830 using the second application.

After processing the sub-task, the second application of second worker730 may produce a sub-result 780 (FIG. 7F). The second application ofsecond worker 230 may transmit, via third network 750, sub-result 780 tofirst worker 130. The first application of first worker 130 may receivesub-result 780, and may complete processing task 755 based on sub-result780. After processing task 755, the first application of first worker130 may produce a result 785 (FIG. 7F) based on the processing of task755. First worker 130 may transmit result 785 to client device 110.

FIGS. 8A-8D illustrate an example of processing a task in an environment800. As shown in FIGS. 8A-8D, environment 800 may include one or more ofthe following components: client device 110, first worker 130, licensingserver 140, second network 720, second worker 730, a first network 810,a web service 820, and third network 750. In practice, environment 800may include additional components, fewer components, differentcomponents, or differently arranged components than are shown in FIG. 8.Additionally, or alternatively, one or more of the components ofenvironment 800 may perform one or more functions described as beingperformed by another one or more of the components of environment 800.

Client device 110, first worker 130, licensing server 140, secondnetwork 720, second worker 730, and third network 750 of FIG. 7 maycorrespond to client device 110, first worker 130, licensing server 140,second network 720, second worker 730, and third network 750 of FIG. 7,respectively. First network 810 may include client device 110, which mayexecute application 160.

In this example, first worker 130 may be accessible via web service 820,second worker 730 may be accessible via second network 720, and clientdevice 110 may be accessible via first network 810. License server 140may be accessible via third network 750. In this example, application160 of client device 110 may require for first worker 130 to use a firstapplication to process a task and for second worker 730 to use a secondapplication to process a portion of the task.

For example, as shown in FIG. 8A, application 160 may create a task 855.Application 160 may transmit, via first network 810, task 855 to webservice 820. Web service 820 may receive task 855 from application 160,and may forward task 855 to first worker 130. Task 885 may includeauthentication credentials associated with client device 110. Firstworker 130 may generate a first authorization request 860 based on theauthentication credentials. First worker 130 may use web service 820 toforward, via third network 750, first authorization request 860 tolicensing server 140. Licensing server 140 may determine, based on theauthentication credentials included in first authorization request 860,that first worker 130 is authorized to process task 855. Accordingly,licensing server 140 may generate and transmit, via third network 750,first authorization 865 (FIG. 8B). Web service 820 may receive firstauthorization 865, and may forward first authorization 865 to firstworker 130.

In one implementation, first worker 130 may determine that a secondapplication is required to process a sub-task of task 855. Task 855 mayfurther include information that authorizes the second application toprocess the sub-task based on a second license (e.g., a non-perpetuallicense). Accordingly, first worker 130 may generate a request 870 toprocess sub-task based on the sub-task and the information that thatauthorizes the second application to process the sub-task. First worker130 may transmit, via third network 750, request 870 to second worker730. In response to request 870, second worker 730 may, based on theinformation that authorizes the second application to process thesub-task, use the second application to process the sub-task 830 inaccordance with the second license.

In another implementation, before generating first authorization request860, first worker 130 may determine that additional processing power(e.g., another worker) is required to process a sub-task of task 855.First worker 130 may include first authorization request 860 in a secondauthorization request for licensing server 140 to provide authorizationto second worker 730 to process the sub-task. When licensing server 140determines that first worker 130 is authorized to process task 855,licensing server 140 may also determine that second worker 730 isauthorized to process the sub-task. Licensing server 140 may generatefirst authorization 865 and a second authorization 875 (FIG. 8C).Licensing server 140 may transmit first authorization 865 to firstworker 130, as described above, and may transmit second authorization875 to second worker 730. After first worker 130 receives firstauthorization 865, first worker 130 may generate request 870 thatdirects second worker 130 to process the sub-task based on secondauthorization 875. First worker 130 may transmit request 870 to secondworker 730. In response to request 870, second worker 730 may processthe sub-task based on second authorization 875.

After processing the sub-task, second worker 730 may produce asub-result 880 (FIG. 8D). Second worker 730 may transmit, via thirdnetwork 750, sub-result 880 to first worker 130. Web service 820 mayreceive sub-result 880, and may forward sub-result 880 to first worker130. First worker 130 may produce a result 885 (FIG. 8D) based onprocessing of task 855 and/or based on sub-result 880. First worker 130may transmit result 885 to application 160 of client device 110.

CONCLUSION

The foregoing description of implementations provides illustration anddescription, but is not intended to be exhaustive or to limit theinvention to the precise form disclosed. Modifications and variationsare possible in light of the above teachings or may be acquired frompractice of the invention.

For example, while series of blocks have been described with regard toprocesses of FIGS. 5 and 6, the order of the blocks may be modified inother implementations. Further, non-dependent blocks may be performed inparallel.

It will be apparent that example aspects, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the embodiments illustrated in the figures. The actual software codeor specialized control hardware used to implement these aspects shouldnot be construed as limiting. Thus, the operation and behavior of theaspects were described without reference to the specific softwarecode-it being understood that software and control hardware could bedesigned to implement the aspects based on the description herein.

Further, certain portions, described herein, may be implemented as“logic” that performs one or more functions. This logic may includehardware, such as an application specific integrated circuit or a fieldprogrammable gate array, or a combination of hardware and software.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit the disclosure of the invention. In fact, many ofthese features may be combined in ways not specifically recited in theclaims and/or disclosed in the specification. Although each dependentclaim listed below may directly depend on only one other claim, thedisclosure of the invention includes each dependent claim in combinationwith every other claim in the claim set.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such. Also, as used herein, the article “a” is intended toinclude one or more items. Where only one item is intended, the term“one” or similar language is used. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise.

What is claimed is:
 1. A method comprising: receiving a task, the taskbeing received over a first network, the task including authenticationcredentials, the task being processed using an application, and thereceiving the task being performed by a computing device; sending theauthentication credentials to a licensing server, the authenticationcredentials being sent over a second network, the second network beingdifferent than the first network, the authentication credentials beingsent prior to processing the task using the application, and the sendingthe authentication credentials being performed by the computing device;receiving authorization information, the authorization information beingreceived over the second network, the authorization informationauthorizing the application to process the task, and the receiving theauthorization information being performed by the computing device;generating, at a first time and based on receiving the authorizationinformation, one or more heartbeat messages, the generating the one ormore heartbeat messages being performed by the computing device;periodically transmitting, over the second network and to the licensingserver, the one or more heartbeat messages, the periodicallytransmitting the one or more heartbeat messages being performed by thecomputing device; receiving, over the second network and at a secondtime, an indication from the licensing server that the task is to beterminated, the second time occurring after the first time, theindication being based on the one or more heartbeat messages, and thereceiving the indication being performed by the computing device; andterminating, based on the received indication, the task, the terminatingbeing performed by the computing device.
 2. The method of claim 1, wherethe one or more heartbeat messages are transmitted while the applicationis processing the task, and the one or more heartbeat messages are usedto determine whether the application remains authorized to continueprocessing the task.
 3. The method of claim 1, where the one or moreheartbeat messages are used to determine billing information for theapplication.
 4. The method of claim 3, further comprising: usingapplication startup information in conjunction with the one or moreheartbeat messages to determine the billing information for theapplication.
 5. The method of claim 1, further comprising: receiving, ata third time, a response from the licensing server, where the responseindicates whether the application remains authorized, and the third timeoccurs before the second time.
 6. The method of claim 1, furthercomprising: producing a result based on the processing of the task. 7.The method of claim 1, where the authentication credentials include atleast one of: a user name, a password, a token, a digital certificate,or a biometric identifier.
 8. The method of claim 1, where theapplication requires a valid license to process the task.
 9. The methodof claim 1, further comprising: sending the authentication credentialswhen the application is initialized.
 10. The method of claim 1, furthercomprising: sending the authentication credentials prior to initializingthe application.
 11. The method of claim 8, where the license identifiesone or more rights.
 12. The method of claim 1, further comprising:processing the authorization information, where, when generating the oneor more heartbeat messages, the method includes: a generating the one ormore heartbeat messages when the processing indicates that theapplication is authorized to process the task.
 13. The method of claim1, where the task is included in a job.
 14. The method of claim 13,where the task is one of a plurality of tasks included in the job. 15.The method of claim 14, where the task is associated with a firstlicense, and another of the plurality of tasks is associated with asecond license.
 16. The method of claim 1, where the task is receivedfrom a scheduler operating on behalf of a client.
 17. The method ofclaim 1, where the authorization includes license information.
 18. Themethod of claim 1, further comprising: providing the authorization tothe application.
 19. The method of claim 1, further comprising: checkingthe authorization using the application; and commencing billingsubsequent to the checking.
 20. A device comprising: a memory to storeinstructions; and a processor to execute the instructions to: receive atask, the task being received over a first network, the task includingauthentication credentials, and the task being processed using anapplication; send the authentication credentials to a licensing server,the authentication credentials being sent over a second network, thesecond network being different than the first network, and theauthentication credentials being sent prior to processing the task usingthe application; receive authorization information, the authorizationinformation being received over the second network, and theauthorization information authorizing the application to process thetask; generate, at a first time and based on receiving the authorizationinformation, one or more heartbeat messages; periodically transmit, overthe second network and to the licensing server, the one or moreheartbeat messages; receive, over the second network and at a secondtime, an indication from the licensing server that the task is to beterminated, the second time occurring after the first time, and theindication being based on the one or more heartbeat messages; andterminate, based on the received indication, the task.
 21. The device ofclaim 20, where the one or more heartbeat messages are transmitted whilethe application is processing the task, and the one or more heartbeatmessages are used to determine whether the application remainsauthorized to continue processing the task.
 22. The device of claim 20,where the one or more heartbeat messages are used to determine billinginformation for the application.
 23. The device of claim 22, where theprocessor is further to: use application startup information inconjunction with the one or more heartbeat messages to determine thebilling information for the application.
 24. The device of claim 20,where the processor is further to: receive, at a third time, a responsefrom the licensing server, where the response indicates whether theapplication remains authorized, and the third time occurs before thesecond time.
 25. The device of claim 20, where the processor is furtherto: produce a result based on the processing of the task.
 26. The deviceof claim 20, where the authentication credentials include at least oneof: a user name, a password, a token, a digital certificate, or abiometric identifier.
 27. The device of claim 20, where the applicationrequires a valid license to process the task, the license identifyingone or more rights.
 28. The device of claim 20, where the processor isfurther to: send the authentication credentials when the application isinitialized.
 29. The device of claim 20, where the processor is furtherto: send the authentication credentials prior to initializing theapplication.
 30. The device of claim 20, where the processor is furtherto: process the authorization information, where the processor, whengenerating the one or more heartbeat messages, is further to: generatethe one or more heartbeat messages when the processing indicates thatthe application is authorized to process the task.
 31. The device ofclaim 20, where the task is associated with a first license, and anothertask is associated with a second license.
 32. The device of claim 20,where the task is received from a scheduler operating on behalf of aclient.
 33. The device of claim 20, where the authorization includeslicense information.
 34. The device of claim 20, where the processor isfurther to: provide the authorization to the application.
 35. The deviceof claim 20, where the processor is further to: check the authorizationusing the application; and commence billing subsequent to the checking.36. A non-transitory computer-readable medium storing instructions, theinstructions comprising: one or more instructions which, when executedby a processor, cause the processor to: receive a task, the task beingreceived over a first network, the task including authenticationcredentials, and the task being processed using an application; send theauthentication credentials to a licensing server, the authenticationcredentials being sent over a second network, the second network beingdifferent than the first network, and the authentication credentialsbeing sent prior to processing the task using the application; receiveauthorization information, the authorization information being receivedover the second network, and the authorization information authorizingthe application to process the task; generate, at a first time and basedon receiving the authorization information, one or more heartbeatmessages; periodically transmit, over the second network and to thelicensing server, the one or more heartbeat messages; receive, over thesecond network and at a second time, an indication from the licensingserver that the task is to be terminated, the second time occurringafter the first time, and the indication being based on the one or moreheartbeat messages; and terminate, based on the received indication, thetask.
 37. The non-transitory computer-readable medium of claim 36, wherethe one or more heartbeat messages are transmitted while the applicationis processing the task, and the one or more heartbeat messages are usedto determine whether the application remains authorized to continueprocessing the task.
 38. The non-transitory computer-readable medium ofclaim 36, where the one or more heartbeat messages are used to determinebilling information for the application.
 39. The non-transitorycomputer-readable medium of claim 38, where the one or more instructionsinclude: one or more instructions to use application startup informationin conjunction with the one or more heartbeat messages to determine thebilling information for the application.
 40. The non-transitorycomputer-readable medium of claim 36, where the one or more instructionsinclude: one or more instructions to receive, at a third time, aresponse from the licensing server, where the response indicates whetherthe application remains authorized, and the third time occurs before thesecond time.
 41. The non-transitory computer-readable medium of claim36, where the one or more instructions include: one or more instructionsto produce a result based on the processing of the task.
 42. Thenon-transitory computer-readable medium of claim 36, where theauthentication credentials include at least one of: a user name, apassword, a token, a digital certificate, or a biometric identifier. 43.The non-transitory computer-readable medium of claim 36, where theapplication requires a valid license to process the task, the licenseidentifying one or more rights.
 44. The non-transitory computer-readablemedium of claim 36, where the one or more instructions include: one ormore instructions to send the authentication credentials when theapplication is initialized.
 45. The non-transitory computer-readablemedium of claim 36, where the one or more instructions include: one ormore instructions to send the authentication credentials prior toinitializing the application.
 46. The non-transitory computer-readablemedium of claim 36, where the one or more instructions include: one ormore instructions to process the authorization information, where theone or more instructions to generate the one or more heartbeat messagesinclude: one or more instructions to generate the one or more heartbeatmessages when the processing indicates that the application isauthorized to process the task.
 47. The non-transitory computer-readablemedium of claim 36, where the task is associated with a first license,and another task is associated with a second license.
 48. Thenon-transitory computer-readable medium of claim 36, where the task isreceived from a scheduler operating on behalf of a client.
 49. Thenon-transitory computer-readable medium of claim 36, where the one ormore instructions include: one or more instructions to provide theauthorization to the application.
 50. The non-transitorycomputer-readable medium of claim 36, where the one or more instructionsinclude: one or more instructions to check the authorization using theapplication; and one or more instructions to commence billing subsequentto the checking.